Voice messaging method and mobile terminal supporting voice messaging in mobile messenger service

ABSTRACT

A mobile terminal supporting a voice messaging method includes a microphone for capturing sound waves and converting the sound waves into an audio signal, a storage unit for storing the audio signal, an audio data generation unit for generating audio data packets with the audio signal, a packet data communication network interface unit for providing a packet data communication network, and a control unit for controlling the microphone, audio storage unit, audio data generation unit, and packet data communication network interface unit to capture the audio signal and transmit the audio signal as audio data packets in response to audio message transmission request entered during a mobile messenger service session.

PRIORITY

This application is a Continuation Application of, and claims priorityunder 35 U.S.C. § 120 to, U.S. application Ser. No. 15/461,036, whichwas filed in the U.S. Patent and Trademark Office on Mar. 16, 2017 andwas a Continuation Application of, and claimed priority under 35 U.S.C.§ 120 to, U.S. application Ser. No. 15/092,085, which was filed in theU.S. Patent and Trademark Office on Apr. 6, 2016, issued on Apr. 25,2017 as U.S. Pat. No. 9,635,525, and was a Continuation Application of,and claimed priority under 35 U.S.C. § 120 to, U.S. application Ser. No.14/087,965, which was filed in the U.S. Patent and Trademark Office onNov. 22, 2013, issued as U.S. Pat. No. 9,338,614 on May 10, 2016, andwas a Continuation Application of, and claimed priority under 35 U.S.C.§ 120 to, U.S. application Ser. No. 11/788,072, which was filed in theU.S. Patent and Trademark Office on Apr. 19, 2007, issued as U.S. Pat.No. 8,605,638 on Dec. 10, 2013, and claimed priority under 35 U.S.C. §119 to Korean Patent Application No. 10-2006-0036634, which was filed inthe Korean Intellectual Property Office on Apr. 24, 2006, and entitled“Voice Messaging Method and Mobile Terminal Supporting Voice MessagingIn Mobile Messenger Service,” the contents of all of which areincorporated herein by reference.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a mobile terminal and, in particular,to a voice messaging method and a mobile terminal supporting the voicemessaging method in a mobile messenger service.

2. Description of the Related Art

With the advance of wireless technologies, mobile communication systemsincluding Code Division Multiple Access (CDMA) system has been developedto provide multimedia communication services in addition to the basicservice of voice communication service.

Keeping pace with popularity of the multimedia communications, mobileterminals become closer to personal computers (PC) in theircapabilities. For example, recent mobile terminals incorporate varioussupplementary functions such as messaging service, image transmission,contact list management, and scheduler functions. Accordingly, themobile terminal must store various kinds of data such as residentialaddresses, internet mail addresses, avatars, and the like, as well ascall numbers.

Rapid growth of such multimedia services has led to the increase ofutilization of mobile terminals and strong demands for various mobileservices including messaging service.

As one of such mobile services, mobile messenger services allowsubscribers to exchange data in real time. The mobile messenger serviceenables the subscribers to exchange memos, files, and other data and toparticipate in a real time chatting and group telephony.

Typically, the conventional mobile messenger services use text messagesfor communication between the subscribers and support a group chattingwhich allow several subscribers to take part in a chatting session.

However, the conventional mobile messenger services have some drawbacksin that voice communication is not supported during a mobile messengerservice session and a person-to-person messaging is not allowed in agroup chatting.

SUMMARY OF THE INVENTION

The present invention has been made in an effort to solve the aboveproblems, and it is an object of the present invention to provide avoice messaging method allowing a mobile terminal operating with thevoice messaging method to transmit a voice message using a mobilemessenger service.

It is another object of the present invention to provide a voicemessaging method allowing a mobile terminal operating with the voicemessaging method to transmit a voice message to one of membersparticipated in a chatting session of a mobile messenger service.

In accordance with an aspect of the present invention, the above andother objects are accomplished by a mobile terminal. The mobile terminalincludes a microphone for capturing sound wave and converting the soundwave into an audio signal; an audio storage unit for storing the audiosignal; an audio data generation unit for generating audio data packetswith the audio signal; a packet data communication network interfaceunit for providing a packet data communication network; a control unitfor controlling the microphone, audio storage unit, audio datageneration unit, and packet data communication network interface unit tocapture the audio signal and transmit the audio signal in the form ofthe audio data packets in response to audio message transmission requestinput in the middle of a mobile messenger service session.

Preferably, the microphone captures a user voice as the sound wave andstores user voice in the form of the audio signal in the storage unit.

Preferably, the audio data generation unit encodes the user voice intoaudio data, segments the audio data into transmission data units, andgenerates the audio data packets contained in the transmission dataunits together with source and destination Internet Protocol addresses.

Preferably, the audio data generation unit performs encoding the uservoice and segmentation of the audio data using an enhanced variable ratecodec.

Preferably, the packet data communication network interface unittransmits the audio data packets to a target terminal participating in amobile messenger service session with the mobile terminal through thepacket data communication network.

Preferably, the mobile terminal further includes an audio decoding unitfor decoding the audio data packets; and a speaker to output the decodedaudio data packets in the form of an audible sound wave, wherein thepacket data communication network unit transfers the audio data packetsreceived in the mobile messenger service session to an audio decodingunit.

In accordance with another aspect of the present invention, the aboveand other objects are accomplished by a voice messaging method for amobile terminal in a mobile messenger service session. The voicemessaging method includes recording a voice message in response to avoice message transmission request input in the middle of the mobilemessenger service session; generating audio data packets containing thevoice message; and transmitting the audio data packets through a packetdata communication network in a predetermined period.

Preferably, generating the audio data packets includes encoding thevoice message; segmenting the encoded voice message into transmissiondata units of a predetermined size; and packing the data units with theaudio data packets together with source and destination InternetProtocol addresses.

Preferably, encoding the voice message includes compressing the voicemessage using an enhanced variable rate codec.

Preferably, the voice messaging method further includes receiving audiodata packets through the packet data communication network in the middleof the mobile messenger service session; decoding the audio datapackets; and outputting the audio data decoded from the audio datapacket in the form of an audible sound wave.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features and advantages of the presentinvention will be more apparent from the following detailed descriptionin conjunction with the accompanying drawings, in which:

FIG. 1 is an overview of a mobile messenger service system according tothe present invention;

FIG. 2 is a message flow diagram illustrating message flows in themessenger service system of FIG. 1;

FIG. 3 is a flowchart of a voice messaging method in a mobile messengerservice according to the present invention; and

FIG. 4 is a block diagram illustrating a configuration of a mobileterminal supporting a voice messaging during a mobile messenger serviceaccording to the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention are described withreference to the accompanying drawings. The same reference numbers areused throughout the drawings to refer to the same or like parts.Detailed descriptions of well-known functions and structuresincorporated herein may be omitted to avoid obscuring the subject matterof the present invention.

Referring to FIG. 1, the mobile messenger service system includes aplurality of mobile terminals 100, 500, and 600, a short message service(SMS) server 200, a packet data core network 300, and a packet dataserving node (PDSN) 400.

The mobile terminals 100, 500, and 600 are provided with a mobilemessenger application. In this embodiment, a host mobile terminal 100transmits an invitation message and client mobile terminals 500 and 600transmit acceptance message to host mobile terminal 100 in response tothe invitation message.

SMS server 200 provides short messaging service to a mobilecommunication network (for example, CDMA network). In this embodiment,SMS server 200 relays the invitation message transmitted by host mobileterminal 100 to client mobile terminals 500 and 600.

Packet data core network 300 establishes communication channels betweenthe mobile terminals using a point-to-point protocol (PPP) andsupporting packet data communication. Packet data core network 300 alsosupports a mobile messenger service after a mobile messenger servicesession is initialized. That is, packet data core network 300 isconfigured to support the real time data exchanges between the host andclient mobile terminals 100, 500, and 600. For example, the packet datacore network bridges the information message transmitted by host mobileterminal 100 to client mobile terminal 500 and 600, bridges theinformation message transmitted by client mobile terminal 500 to hostmobile terminal 100 and client mobile terminal 600, and bridges theinformation message transmitted by client mobile terminal 600 to hostmobile terminal 100 and client mobile terminal 500.

An operation of the above-structured messenger service system isdescribed with reference to FIG. 2.

Referring to FIG. 2, if a command input for the mobile messenger serviceis detected while operating in a normal mode, host mobile terminal 100activates the messenger application in step S105. Next, host mobileterminal 100 generates a buddy list on the basis of a user command instep S110. After the buddy list is generated, host mobile terminal 100transmits a connection request message to PDSN 400 in step S115 andassigned an Internet Protocol (IP) address at step S120 so as toestablish a point-to-point channel.

The buddy list provides a group of members registered for the mobilemessenger service (so called, counterparty user lists). Preferably, thebuddy list is created with the candidate participants selected from thesubscribers stored in the mobile terminal. However, the participants canbe selected in such a manner that the service subscribers are listed ina normal phonebook with a specific indicator and choosing theparticipants among the subscribers listed in a normal phonebook.

After generating the buddy list, host mobile terminal 100 transmits aninvitation message to the client mobile terminals of the candidateparticipants. In the embodiment, the invitation message is transmittedto client mobile terminal 500 as an example. That is, host mobileterminal 100 registers client mobile terminal 500 to the buddy list atstep S110, transmits an invitation message to the SMS server in stepS125. Upon receiving the invitation message, SMS server 200 forwards theinvitation message to client mobile terminal 500 in step S130. Theinvitation message is transmitted with the IP address assigned to hostmobile terminal 100 at step S115. The invitation message also containsinformation of identification number of host mobile terminal 100 andport number for a current session in addition to the IP address.

Upon receiving the invitation message, client mobile terminal 500 checksthat the invitation message is a mobile messenger service message, andactivates the messenger application in step S135. Next, client mobileterminal 500 extracts the information on the host mobile terminal, i.e.the identification number and current session port number of host mobileterminal 100 in step S140.

Next, client mobile terminal 500 is coupled with PDSN 400 through a PPPconnection in step S145 and assigned an IP address from PSDN 400 in stepS150. If an IP address is assigned, client mobile terminal 500 transmitsan acceptance message to PDSN 400 in accordance with a user command instep S155. Upon receiving the acceptance message, PDSN 400 forwards theacceptance message to host mobile terminal 100 in step S160.

Since client mobile terminal 500 knows the IP address of host mobileterminal 100 through the invitation message, client mobile terminal 500transmits the acceptance message with the IP address of the host mobileterminal as a destination address and the IP address assigned from PSDN400 as a source address. Preferably, the acceptance message alsocontains information on a protocol, port number, and authentication inaddition to the IP address information.

Upon receiving the acceptance message, host mobile terminal 100 updatesits buddy list so as to maintain the client mobile terminal transmittingthe acceptance message in the buddy list and removes other candidatemobile terminals that do not transmit an acceptance message in stepS165. Next, host mobile terminal 100 transmits the updated buddy list toclient mobile terminal 500 via the PDSN in steps S170 and S175. That is,host mobile terminal 100 transmits the updated buddy list to PSDN(S170), and the PDSN forwards the updated buddy list to client mobileterminal 500.

If host and client mobile terminals 100 and 500 share the buddy list,the mobile messenger service starts based on the IP network in stepS180. That is, the host and client mobile terminals are connected toPDSN 400 such that IP-based mobile messenger service is provided betweenthe host and client mobile terminals.

It is assumed that the mobile messenger service is initialized throughthe procedure of FIG. 2 such that the host and client mobile terminals100 and 500 are in a mobile messenger service session. In thisembodiment, the voice messaging method is described with an exemplarysituation in which host mobile terminal 100 transmits a voice message toclient mobile terminal 500.

Referring to FIG. 3, after a messenger service session is establishedbetween the host and client mobile terminals 100 and 500 in step S205,and the host and client mobile terminals operate in a text exchange modein steps S210 and 5305.

Host mobile terminal 100 detects if a command input for transmitting avoice message has been issued in step S215. If a voice message commandinput is detected, host mobile terminal 100 starts recording an audio(for example, voice) and disables text messaging in step S220. Forexample, if a user inputs a voice messaging request command, host mobileterminal 100 records a voice input right after the voice messagingrequest command is received. For receiving and processing the voice,host mobile terminal 100 includes a microphone and audio storage unitsuch that the audio signal input through the microphone is stored in theaudio storage unit.

Host mobile terminal 100 detects whether a command for stopping thevoice recording is issued in step S225 while the voice recording isprogressing.

If a voice record stop command is detected in step S225, the host mobileterminal stops recording the voice, re-enables the text-messaging, andgenerates an audio file with the audio recorded before the detectedvoice record stop command in step S230. At this time, host mobileterminal 100 encodes the recorded voice within an audio file and thensegments the audio file in available transmission size. In thisembodiment, an Enhanced Variable Rate Codec (EVRC) is used forcompressing the recorded voice. The compressed and segmented audio dataare contained in data fields of audio data packets each having an IPheader of which source and destination fields are set to the IPaddresses of the host and client mobile terminals.

Next, host mobile terminal 100 transmits the audio data packets toclient mobile terminal 500 in step S235.

If a reception of the audio data packet is detected, client mobileterminal 500 determines if all the audio data packets are successfullyreceived in step S310. If all the audio data packets are successfullyreceived, client mobile terminal 500 decodes the audio packets torestore the audio file in step S315. That is, client mobile terminal 500designates a time duration for receiving the audio data packets and thendecodes the audio data packets received in the time duration to restoredthe audio file. The decoding process is performed with reference to theaudio data segmentation information implied within the headers of theaudio data packets.

After the audio data packets are successfully decoded and restored intothe transmitted audio file, client mobile terminal 500 replays the audiofile in step S320. It is preferred that the client mobile terminaldetermines if it is in an audio input state and start replays of theaudio file when it is not in an audio input state.

Next, client mobile terminal 500 determines if a command for terminatingthe messenger service session is issued in step S325. If a sessiontermination command input is detected, the client mobile terminal endsthe messenger service session in step 5330. If no session terminationcommand is detected, the client mobile terminal repeats steps 305 to325.

Meanwhile, after transmitting the audio data packets at step S235, hostmobile terminal 100 determines if a session termination command input isdetected in step 5240. For example, if a session termination command isinput by a user's key manipulation or received from client mobileterminal 500, the host mobile terminal ends the messenger servicesession in step S245.

In this embodiment outlined in FIG. 3, host mobile terminal 100 startsrecording a voice in response to an audio transmission request command,performs compression and segmentation on the recoded audio data, anddirectly transmits the audio in the form of audio data packets to clientterminal 500. That is, the voice messaging is carried out between thehost and client mobile terminals with engagement of any mobilecommunication system and server.

Accordingly, it is possible to transmit a voice message to a specificcounterparty mobile terminal among the participant terminals in a mobilemessenger service while maintaining the mobile messenger servicesession.

FIG. 4 shows an exemplary configuration of the host mobile terminal inthe FIGS. 1 to 3. However, client mobile terminals 500 and 600 can beimplemented with the same configuration. The configuration of the hostmobile terminal is determined by a transmission of the invitationmessage.

Referring to FIG. 4, host mobile terminal 100 includes a microphone 110,an audio storage unit 120, an audio data generation unit 130, a PDSNinterface unit 140, an audio decoder 150, a user interface unit 160, acontrol unit 170, and a radio frequency interface 180, and a storageunit 190.

Microphone 110 captures a sound wave (for example, a voice) and convertsthe sound wave into electrical signals. That is, microphone 110 receivesa user voice in the mobile messenger service session and stores the uservoice into audio storage unit 120 in the form of audio data, under thecontrol of control unit 170.

Audio storage unit 120 stores the audio signals input through microphone110. That is, audio storage unit 120 starts and ends recording the voicein response to recording start and end commands generated by controlunit 170.

Audio data generation unit 130 converts the audio signal stored in audiostorage unit 120 into a data format suitable for PSDN 400. For example,audio data generation unit 130 segments the audio data into transmissiondata units of predetermined size and compresses the transmission dataunits in a predetermined coding scheme. Preferably, the transmissiondata units are compressed using an Enhanced Variable Rate Codec (EVRC).The transmission data units are carried by the audio data packets eachhaving a header contained the IP address of host mobile terminal 100 asa source address and the IP address of client mobile terminal 500 as adestination address.

PDSN interface unit 140 is responsible for data communication with PDSN400 (see FIG. 2). Particularly, PDSN interface unit 140 allows hostmobile terminal 100 to communicate with other mobile terminalsregistered in the buddy list for the mobile messenger service.Particularly, PDSN interface unit 140 transfers the audio data packetsgenerated by audio data generation unit 130 to the destination address,i.e. client mobile terminals 500 and 600 and receives an audio datapacket transmitted by client mobile terminals 500 and 600 that areparticipated in a mobile messenger service session.

Audio decoding unit 150 decodes the audio data packets received throughPDSN interface unit 140. That is, audio decoding unit 150 decompressesthe EVRC-coded audio data packets.

User interface unit 160 provides a graphic interface in order for a userto control the operation of host mobile terminal 100. Particularly, userinterface unit 160 receives input commands for transmitting theinvitation message and audio data and transmits the commands to controlunit 170.

Control unit 170 controls the operation of host mobile terminal 100 onthe basis of the user commands and predetermined events associated withthe applications.

If an audio message transmission request is entered, control unit 170controls microphone 110, audio storage unit 120, audio data generationunit 130, and PDSN interface unit 140 for recording audio signal andtransmitting the audio signal in the form of the audio data packet. Therecoded audio signal is formatted into audio data packets and thentransmitted to client terminal 500.

Control unit 170 also controls audio decoder 150 to process the audiodata packets received through PDSN interface 140 and output the audiodata though a speaker (not shown) as an audible sound wave.

Preferably, control unit 170 controls such that the text messageexchange is stopped while the audio data packets are transmitted orreceived. That is, control unit 170 controls host mobile terminal 100 tooperate in a text exchange mode and to switch the operation mode to theaudio messaging mode in response to an audio data transmission requestcommand input through PDSN interface unit 140 or when received an audiodata packet from a client mobile terminal. In this case it is preferredto stop the text exchange. This is because host terminal 100 exchangesthe text and audio data through a virtual port (for example, socket).

Radio frequency interface unit 180 controls the voice communication ofthe host mobile terminal. Radio frequency interface unit 180 isresponsible for transmitting and receiving an invitation message in theform of a short message via SMS server 200 (see FIG. 2).

Storage unit 190 stores an operating system, application programs, andthe information related to the operations of application programs.Particularly, storage unit 190 stores a phonebook 191, a messengerprogram, and a buddy list 195. Buddy list 195 provides the informationof members of a group for communicating through the mobile messengerservice.

The voice messaging method of the present invention enables transmittinga voice message to a specific member participated in a mobile messengerservice session without engagement of a mobile communication system or aserver.

As described above, the voice messaging method and mobile terminalsupporting the voice messaging method according to the present inventionenables a user participating in a mobile messenger service session totransmit a voice message to another participant of the session withoutengagement of a mobile communication system or a server. In the casewhere a single counterparty user is participating in the mobilemessenger service session, the participants can communicate with eachother using a voice messaging function in the mobile messenger servicerather than through costly voice communication channel, resulting incost effective voice communication.

Although exemplary embodiments of the present invention have beendescribed in detail hereinabove, it should be clearly understood thatmany variations and/or modifications of the basic inventive conceptsherein taught which may be made by those skilled in the present art willstill fall within the spirit and scope of the present invention, asfurther defined by the appended claims.

What is claimed is:
 1. A portable communication device comprising: amicrophone; communication circuitry; and a processor adapted to: executea specified application to communicate with an external electronicdevice; receive, via a user interface corresponding to the specifiedapplication, a request to record an audio message; in response toreceiving the record request, record an audio input received via themicrophone to generate the audio message and disable the user interfacefrom receiving text input; receive a request to transmit the audiomessage; and in response to receiving the transmit request, transmit,using the communication circuitry, at least part of the audio message tothe external electronic device and re-enable the user interface toreceive the text input.
 2. The portable communication device of claim 1,wherein the processor is further adapted to: execute, as at least partof the specified application, a messenger application to exchange amessage with the external electronic device.
 3. The portablecommunication device of claim 1, wherein the processor is furtheradapted to: activate a graphic user interface as at least part of theuser interface and receive the record request via the graphic userinterface.
 4. The portable communication device of claim 1, wherein theprocessor is further adapted to: transmit the at least part of the audiomessage in portions having a specified size.
 5. The portablecommunication device of claim 1, wherein the processor is furtheradapted to: transmit the at least part of the audio message in a form ofat least one data packet via a packet data network.
 6. The portablecommunication device of claim 1, wherein the processor is furtheradapted to: transmit the at least part of the audio message using theInternet.
 7. The portable communication device of claim 1, wherein theexternal electronic device includes a first external electronic deviceand a second external electronic device, and wherein the processor isfurther adapted to: transmit the at least part of the audio message tothe first external electronic device or the second external electronicdevice, where the first external electronic device or second externalelectronic device is selected to receive transmission based at least inpart on a user input.
 8. The portable communication device of claim 1,wherein the processor is further adapted to: receive, using thecommunication circuitry, at least one text from the external electronicdevice via a packet data network.
 9. The portable communication deviceof claim 1, wherein the processor is further adapted to: transmit, usingthe communication circuitry, at least one text corresponding to a shortmessage service via a short message service server before the portablecommunication device is connected to the external electronic device viaa packet data network.
 10. The portable communication device of claim 1,further comprising: memory to store a phonebook including at least onecontact information corresponding to the external electronic device,wherein the processor is further adapted to: select the externalelectronic device to receive the at least part of the audio messagebased at least in part on a determination that the at least one contactinformation is marked as available to receive the at least part of theaudio message.
 11. A method comprising: executing, at an electronicdevice including a microphone and communication circuitry, a specifiedapplication to communicate with an external electronic device;receiving, via a user interface corresponding to the specifiedapplication, a request to record an audio message; in response toreceiving the record request, recording an audio input received via themicrophone to generate the audio message and disable the user interfacefrom receiving text input; receiving a request to transmit the audiomessage; and in response to receiving the transmit request,transmitting, using the communication circuitry, at least part of theaudio message to the external electronic device and re-enabling the userinterface to receive text input.
 12. The method of claim 11, whereinexecuting the specified application comprises: executing, as at leastpart of the specified application, a messenger application to exchange amessage with the external electronic device.
 13. The method of claim 11,wherein receiving the record request comprises: receiving the recordrequest via a graphic user interface activated as at least part of theuser interface.
 14. The method of claim 11, wherein transmitting atleast part of the audio message comprises: transmitting the at leastpart of the audio message in a form of at least one data packet via apacket data network.
 15. The method of claim 11, wherein the externalelectronic device includes a first external electronic device and asecond external electronic device, and wherein transmitting at leastpart of the audio message comprises: transmitting the at least part ofthe audio message to the first external electronic device or the secondexternal electronic device, where the first external electronic deviceor second external electronic device is selected to receive transmissionbased at least in part on a user input.
 16. The method of claim 11,further comprising: receiving, using the communication circuitry, atleast one text from the external electronic device via a packet datanetwork.
 17. The method of claim 11, further comprising: selecting theexternal electronic device to receive the at least part of the audiomessage based at least in part on a determination that at least onecontact information corresponding to the external electronic device in astored phonebook is marked as available to receive the at least a partof the audio message.
 18. A non-transitory machine-readable storagedevice storing instructions that, when executed by one or moreprocessors, cause the one or more processors to perform operationscomprising: executing, at an electronic device including a microphoneand communication circuitry, a specified application to communicate withan external electronic device; receiving, via a user interfacecorresponding to the specified application, a request to record an audiomessage; in response to receiving the record request, recording an audioinput received via the microphone to generate the audio message anddisable the user interface from receiving text input; receiving arequest to transmit the audio message; and in response to receiving thetransmit request, transmitting, using the communication circuitry, atleast part of the audio message to the external electronic device andre-enabling the user interface to receive text input.
 19. Thenon-transitory machine-readable storage device of claim 18, wherein theoperation of receiving the record request comprises: receiving therecord request via a graphic user interface activated as at least partof the user interface.
 20. The non-transitory machine-readable storagedevice of claim 18, wherein the operation of transmitting at least partof the audio message comprises: transmitting, using the communicationcircuitry, the at least part of the audio message in a form of at leastone data packet via a packet data network.